Guideline: Tips - Determine The Test Strategy (AST)

With iterative or agile system development, the test strategy should focus on regression tests in respect of the many interim releases (iterations, increments). Also, the test (strategy) should be restricted to the characteristics of the interim release and not formulate a strategy as if it concerns the final release. This appears easier than it is, for in the PRA the users provide their risk estimate on the basis of the expected final release. See also Test Types.
At the setting up of the strategy, the test manager should make as much allowance as possible for the consideration of costs, time and skills required. If he knows that there is only a very limited budget or that the available people have no experience in testing, he should avoid proposing ‘impossible’ strategies, such as very expensive tests or very thorough test-design techniques (to prevent too may feedback cycles).
It is advisable, when choosing between thorough and light testing of a characteristic/object part, to make an immediate inventory of the test basis to be used, as the availability and degree of detail of the test basis can influence the budget and planning. Allowance can be made for this during these steps.